PostgreSQL - SQL error when add new tag#6314
PostgreSQL - SQL error when add new tag#6314alikon wants to merge 11 commits intojoomla:stagingfrom alikon:patch-8
Conversation
#### Steps to reproduce the issue go to the article manager and create a new article or edit an existing article In the tags field create a tag on the fly or in other words don´t select an existing tag but put in a new tag. Then hit the "Save". #### Expected result The article is saved with the new added tag #### Actual result the tag field is cleared and the article is not saved #### System information PostgreSQL 9.3.5 Joomla 3.4.0 #### Additional comments As suggested added a sanity check for NOT NULL FIELDS fix #6104
whitespace at end of line
i hate whitespaces at end of line
|
@alikon Please try the following:
Save failed with the following error: SQL=INSERT INTO udzse_contentitem_tag_map Another test case:
Under mssql to get the following error when you try to add a new tag to an existing article: Save failed with the following error: [Microsoft][SQL Server Native Client 11.0][SQL Server]Error converting data type varchar to bigint.SQL=INSERT INTO ufv5y_tags VALUES ('1','1','17','18','2015-03-05-20-25-47','2015-03-05-20-25-47','Stiege','('''')','1','((0))','2015-03-05 20:25:47','1','{}',' ',' ','{}','((0))','2015-03-05 20:25:47','('''')','((0))','2015-03-05 20:25:47','{}','{}','((0))','*','((1))','2015-03-05 20:25:47','2015-03-05 20:25:47') |
|
@waader maybe i will able to find a fix to mssql too |
|
@alikon I modified your sql slightly to SELECT column_name as Field, data_type as Type, is_nullable as 'Null', column_default as 'Default' and this gives the following back: id bigint NO NULL |
|
@waader can you send the results in a more viewable (tabular/matrix) way even with screenshot I'm not sure I've fully understand the results |
|
Thx now is clear, let me prepare a fix..... |
the postgresql driver return a "bad" default value for fields of type (TEXT, CHARACTER VARYING) declared NOT NULL WITH DEFAULT solve #6314
the mssql driver return a "bad" default value for fields of type nvarchar declared NOT NULL WITH DEFAULT
|
@waader |
|
@test works much better now, but there is one case I would like you to try:
|
|
@waader |
|
@alikon works fine with postgresql now. Mssql is another chapter and not in the scope of this pr. Thanks! |
|
Confirmed issue This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/6314. |
|
Two tests setting RTC This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/6314. |
|
Thank you @alikon! Merged. |
No need for a hackish workaround for an unused table column.

Steps to reproduce the issue
go to the article manager and create a new article or edit an existing article In the tags field create a tag on the fly or in other words don´t select an existing tag but put in a new tag. Then hit the "Save".
Expected result
The article is saved with the new added tag
Actual result
the tag field is cleared and the article is not saved
System information
PostgreSQL 9.3.5
Joomla 3.4.0
Additional comments
As suggested added a sanity check for NOT NULL FIELDS
fix #6104